[DE]Glen

9 minutes ago, TheGreatMorph said:

My Warframe crashes on DirectX11, when SSAO Quality is set to Very High. With, or without overlays like steam or geforce. Doesn't crash when set to High though, and does not crash even on Very High if using DirectX12. RTX 4070Ti GPU. Do you guys have any similar reports, or is this an issue on my side?

Fixes for SSAO Very High are coming with next hotfix (we just need to wait for all platforms to get through cert).

16 hours ago, Dalewyn said:

@[DE]Glen Can you also clarify on the duplicate SKU entries on the previous pie chart? Duplicate 14700K entries, for example. I'm assuming you guys meant 14600K or something, but would be nice to have it clarified and corrected while we're here.

It looks like subtitles in the way crash logs report the base CPU frequency; evidently some are "Core i7-14700K 3418MHz" and some are "Core i7-14700K 3417MHz" in the logs; the base clock estimate was originally written in 2003 to try to identify overclocked systems when analyzing crashes a...

There has been some confusion about our recent Dev Workshop post describing an issue we ran into with recent Intel processors. To be clear: we were describing a specific issue and how we fixed it on one machine with the hope that it might help others.

We have over 100 workstations containing Intel 13th and 14th-generation processors deployed at Digital Extremes and we were only having problems with one of them; after...

While investigating crashes in Warframe we came across a particular series that were not crashing in our code (they were crashing in nvgpucomp64.dll, a component of Nvidia drivers). After aggregating hundreds of reports from helpful players we discovered a pattern: almost all were coming from systems with 13th and 14th generation Intel processors.

Luckily we found a staff member who would encounter these crashes on his home computer. Curiously, his computer at the office was fine: he was playing with the same loadout, the same customizations, with the same people, but he would only crash at home.

He wasn’t over-clocking anything and it was a new machine so there was no reason to expect problems. We tried all of the usual ...

I've never seen this before; this sounds like something the Support Desk can help you with, especially if you go to the launcher settings and Send Logs so we can see what's going on.

If you want to help debug you might try disabling GPU particles for a while to see we can rule them out as a suspect:

The only downside is you might hit some other unrelated crash and you won't be able to know from the WAR-number - but since this is our most common crash *by far* if it helps it should probably be obvious.

Scratch that -- we found a bunch of reports with them disabled so that rules out GPU particles as a suspect

I took some pictures at TennoCon before I had to run back to the office to deal with the servers:

https://www.flickr.com/photos/199018099@N07/sets/72177720310773156/

It was amazing to meet people from all over the world and I was blown away to hear about groups of friends that all came from different cities to be together with us. What a community!

Sorry for the upheaval: we just updated the Recommended Official Layouts (we couldn't do this until we'd released the update and there was some difficulty getting them ported over from our Test cluster).

If you're using Steam Input for Warframe (ie: for a PS4 or Steam Controller that doesn't work with the native XInput) restart Steam to refresh the list, edit your Warframe Controller settings in steam, select a layout, and you should see an updated recommended layouts for Playstation, Xbox, Nintendo Switch, Steam, and Steam Deck controllers now:

New Internet who dis?

https://twitch.tv/DE_BadHorse

We've been able to narrow down the issue and can confirm this is a problem with a specific ISP.

If you have a PC you can confirm that you have this problem by:

• Opening a command prompt and typing “nslookup api.warframe.com” 
  • if it reports 23.40.172.184 as one of the addresses, your DNS server is returning stale information and is effected. 
• Unfortunately it seems there is a pool of addresses returned and you may not see the bad one immediately (this is why the game can sometimes work but then will fail at random).
• Tip: press the up arrow and then enter to re-run the same command a few times – in normal circumstances the addresses resolved might change every 20 seconds or so.

As others have pointed out in this thread there is a workaround: you don’t have to use the DNS servers provided by your ISP. You can switch to a free DNS server locally on your PC, console or on yo...

Let's see if my internet is fixed...

htttps://twitch.tv/DE_BadHorse

Today on https://twitch.tv/DE_BadHorse

More Mirror Defense today on twitch.tv/DE_BadHorse

I wanna rock today on twitch.tv/DE_BadHorse

17 minutes ago, Horactius said:

Thank you for the updates! I didn't expect decorations to affect RAM usage when buying things in open world at all. Thank you for optimizing this 😃

Edit: I wanted to add that clicking and then buying things seems to be more effective in increasing the RAM usage than clicking on something, returning, and then clicking on something new over and over again but I'm not 100% sure.

The code has been dramatically optimized for the next update however your 2741 placed decorations will still tax certain parts of the purchasing UI to some extent. The problem is we need to cross-reference decorations you've placed with the products being displayed to show how many you might already own and this is complicated to handle things like bundles. It's also a temporary memory expense: once it's cross-referenced the counts it can release the m...

18 hours ago, Horactius said:

Hi, sorry for the late reply. Yes, I'm still experiencing this and have managed around it ever since I know about the out of memory problem. I have communicated this with [DE]Purzzle but couldn't find anything that could've caused this yet after comparing setting and spec. Right now, I suspect that this have something to do with my hardware.

Wow! Okay, what are you buying specifically? I'd like to clone your account to the dev cluster and retrace your steps if I can.

Found something: just going to trade tokens with Father and then cancelling the purchase over and over bloats a lot of memory (but it comes down after) -- we'll optimize this now.

Edit 2: it's related to the number of placed decorations in your ship which is why not everyone sees this.

On 2022-12-29 at 3:33 AM, Horactius said:

I'm not sure if this is the bug you guys are after but I have something that might be related to it.

I notice that my game keep crashing whenever I was buying multiple items from the store from open world NPCs for a while now. It's been getting more consistent too after I tried figuring out what made my game crash and in my case, it would almost always be crashing after buying at least 3 items from the store right after another and that's that. I didn't think much more of it until I saw this thread yesterday. Then I started paying attention to my RAM when I'm on open world and trying to buy items.

This is a very interesting observation! Is it still happening for you? I tried myself just now and bought a whole bunch of stuff from Yonta and couldn't move the needle. I wonder if there's some sort of local setting that aggravates this.

Farming Molt Augmented today on https://twitch.tv/DE_BadHorse

Kung-Fu Fighting today on https://twitch.tv/DE_BadHorse

Let's see how my connection to https://twitch.tv/DE_BadHorse feeling today...